Skip to main content
Version: Next

Overview

Drupal based CMS​

  • The Navida Pro Platform is designed with a high degree of flexibility and customization in mind, particularly in how it allows for dynamic configuration. Here's an elaboration on the highlighted features:

  • Dynamic Configuration: The platform's ability to be configured dynamically suggests that changes can be made to the system's behavior and appearance without the need for redeployment or downtime. This could be achieved through a user-friendly interface or API that allows administrators or authorized users to adjust settings on the fly.

  • AMP Frontend Customization: AMP, which stands for Accelerated Mobile Pages, is a web component framework and a website publishing technology developed by Google which has the mission to provide a user-first format for web content. The mention of AMP Frontend customization indicates that the Navida Pro Platform is capable of serving content optimized for mobile devices and that this content can be tailored through various configuration options.

  • Configuration Options - Styling and Feature Options: The platform offers a range of configuration options that affect both styling and features. Styling options might include themes, color schemes, font choices, and layout adjustments that can be altered to match branding requirements or user preferences. Feature options could involve enabling or disabling certain functionalities, adjusting performance settings, or modifying how certain aspects of the platform operate.

  • Live Editing by AOK: The term "AOK" is not universally defined in this context, but it could refer to a role, team, or user with the authority to make these live edits. The ability to edit configurations live implies that changes can be made in real-time, with immediate visibility of those changes on the platform. This is particularly useful for responding quickly to user feedback or market demands.

Navida Pro Platform is a robust and adaptable system that can be tailored to meet specific needs without significant delays or technical challenges. This level of customization can greatly enhance user experience and operational efficiency, thanks to the powerful CMS system behind.

  • Drupal-Powered CMS: Drupal is an open-source content management framework written in PHP. It provides a back-end framework for at least 2.3% of all websites worldwide, ranging from personal blogs to corporate, political, and government sites. As the CMS in this scenario, Drupal is responsible for content management, user management, and delivering content to front-end systems.

  • PostgreSQL Database: PostgreSQL is a powerful, open-source object-relational database system that uses and extends the SQL language combined with many features that safely store and scale the most complicated data workloads. In this context, PostgreSQL is used to store all the content, configurations, and other relevant data managed by the CMS.

  • BFF (Backend for Frontend) Services: The BFF pattern involves creating a backend service layer specifically tailored to the needs of each individual client application (e.g., web, mobile, desktop). These services act as an intermediary between the front-end systems and the CMS, providing content and configurations in a way that's optimized for each client.

  • Content Repository: The CMS serves as a repository for static content such as images, static HTML files, and JSON files. This means that these types of content are stored and managed within the CMS and can be served to the front-end systems as needed.

  • Dynamic Feature Modification: The CMS allows for dynamic modification of features in the front-end systems through feature toggles and configurations. Feature toggles are a powerful technique, allowing teams to modify system behavior without changing code. Feature configurations are settings that can be adjusted to alter the behavior of a feature.

  • System of Record: For the features listed below , the CMS also acts as a system of record. This means it is the authoritative data source for those features. Any changes or updates to the features' behavior or configurations are managed within the CMS, ensuring consistency and reliability across the front-end systems that rely on this information.This data is also an AOK specific one means each AOK can create and maintain its own contents and configurations

  • Consent management

  • Challenges ( sports, mental , hybrid)

  • motivation

  • VorsorgeKompass

    CMS in Navida Pro universe is a central hub for managing and delivering content and configurations to various front-end systems. It provides flexibility and control over how content is presented and how features behave, with the ability to make changes dynamically and ensure that all systems are using the most up-to-date information.